Peer-to-peer download with quality of service fallback

ABSTRACT

An embodiment relates generally to a method for playing for a file. The method includes initiating a playback for a selected file on a reserved server, where the selected file is also distributed in segments across a peer-to-peer network. The method also includes initiating a retrieval of the selected file from the peer-to-peer network or reserved server and ordering the retrieved segments of the selected file for playback. The method further includes switching playback of the selected file between the peer-to-peer network and reserved server according to the real-time performance and availability of the peer-to-peer network and reserved server.

FIELD

This invention relates generally to file transfers, more particularly, to methods, apparatus and systems for peer-to-peer download with quality of service fallback.

DESCRIPTION OF THE RELATED ART

File transfers in a network computer system is a generally well-known concept. For example, in the early days of the Internet, file transfers were accomplished by connecting to a destination computer and executing a file transfer command.

Currently, the file transfers may include video, image, audio, application, or other similar information. The files are typically stored in a single server acting as an access point. A user may be assured that the file would be available. However, the server processing a file transfer request has to allocate network bandwidth and server resources to process the request. Accordingly, a server has less available resources to service other types of requests, and thus lowering the overall performance of the server.

One solution to avoid tying up a server for file transfer is to use a peer-to-peer (P2P) network. In general, the P2P network is a computer network that relies primarily on the computing power and bandwidth of the participants in the network rather than concentrating it in a relatively low number of servers. P2P networks are typically used for connecting nodes via largely ad hoc connections.

Although the P2P network can resolve the demand on a server, this solution also has drawbacks and disadvantages. For example, the download or playback of a file is not guaranteed. More particularly, since the file is distributed across the peers in the network, file playback or download may be disrupted by one of the peers either being busy or down.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features of the embodiments can be more fully appreciated, as the same become better understood with reference to the following detailed description of the embodiments when considered in connection with the accompanying figures, in which:

FIG. 1 illustrates an exemplary system in accordance with an embodiment;

FIG. 2 illustrates an exemplary quality of service client in accordance with another embodiment;

FIG. 3 illustrates an exemplary flow diagram implemented by the quality of service client in accordance with yet another embodiment; and

FIG. 4 illustrates an exemplary computing platform for executing the quality of service client in accordance with yet another embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

For simplicity and illustrative purposes, the principles of the present invention are described by referring mainly to exemplary embodiments thereof. However, one of ordinary skill in the art would readily recognize that the same principles are equally applicable to, and can be implemented in, all types of networked computer systems, and that any such variations do not depart from the true spirit and scope of the present invention. Moreover, in the following detailed description, references are made to the accompanying figures, which illustrate specific embodiments. Electrical, mechanical, logical and structural changes may be made to the embodiments without departing from the spirit and scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense and the scope of the present invention is defined by the appended claims and their equivalents.

Embodiments relate generally to systems, methods and apparatus for peer-to-peer (P2P) download with a guarantee of quality of service. The method includes initiating a playback for a selected file on a reserved server, where the selected file is also distributed in segments across a peer-to-peer network. The method also includes initiating a retrieval of the selected file from the peer-to-peer network or reserved server and ordering the retrieved segments of the selected file for playback. The method further includes switching playback of the selected file between the peer-to-peer network and reserved server according to the real-time performance and availability of the peer-to-peer network and reserved server.

In one embodiment, a guaranteed quality of service (GQOS) client may be configured to provide data (e.g., music, video) at a minimum quality of service from a P2P system. The GQOS client may implement a heuristic or algorithm that comprises initiating a data service from a dedicated server. The GQOS client may then initiate a P2P network to gather the later segments of the selected file. As the later segments are ready, the GQOS client queues the next segment from the P2P network. If the GQOS client determines that an upcoming segment is not available, the GQOS client may then retrieve that segment from the reserved server. Accordingly, the majority of the file may be gathered by the P2P network members and maintain a level of desired service while not occupying the resources of the reserved server. Alternatively, the GQOS client may initiate retrieval first from the reserved server and then turn to the P2P network. As another variation, the GQOS client may initiate both the reserved server and P2P network and schedule transitions between them based on their real-time performance.

FIG. 1 illustrates an exemplary system in accordance with an embodiment. It should be readily apparent to those of ordinary skill in the art that the system 100 depicted in FIG. 1 represents a generalized schematic illustration and that other components may be added or existing components may be removed or modified. Moreover, the system 100 may be implemented using software components, hardware components, or combinations thereof.

As shown in FIG. 1, the system may include a plurality of reserved servers 105, a plurality of peers 110, and a user platform 115. The reserved servers 105, the peers 110 and the client 115 may be coupled with a network 120. The network 120 may be a local area network, a wide area network or a combination thereof. The local area network may be an IEEE 802.xx network, ad hoc network, or combinations thereof. The wide area network may be X.25, ATM, SONET, Internet or combinations thereof.

The reserved servers 105 may be a computing machine or platform configured to at least store files 125 for download or playback for the users such as user platform 115. The files may be music, video and/or application files. The reserved servers 105 may also execute an operating system 130 to provide, among other things, the functionality for playback or download. The reserved servers 105 may be implemented with server platforms as known to those skilled in the art from Intel, Advanced Micro Devices, Hewlett-Packard, etc.

The peers 110 may be a collection of servers and/or clients participating in a peer-to-peer (P2P) network. The peers 110, collectively, store the same files as the reserved servers 105. However, each peer 110 may store segments of an individual file in a local memory 140. The entire file may be retrieved by using the underlying P2P protocol 135 such as Bit-Torrent, KaZaa, Napster, CAN, CHORD, or other similar P2P protocol. Of note, in addition to typical public torrents, the torrent used by embodiments of the present invention can be private or secure (e.g., personal video).

Although FIG. 1 depicts the reserved servers 105 and the peers 110 as separate entities, it should be readily obvious to one of ordinary skill in the art that the separation is a logical separation and done for the sake of clarity. In various embodiments, the reserved servers 105 and peers 110 may be distributed, intermingled or co-located in a geographic sense.

The user platform 115 may be computing machine or platform configured to execute secure and open applications through an operating system 145. The operating system 145 may be configured to provide a software platform to provide services, such as download or playback of files. The user platform 115 may be implemented with personal computers, workstations, thin clients, thick clients, or other similar computing platform. The user platform 115 may use operating systems such as Linux, Windows, Macintosh or other available operating systems known to those skilled in the art.

In some embodiments, the user platform 115, among other functionalities, may execute a guaranteed quality of service (GQOS) client 150. The GQOS client 150 may be configured to provide a user the capability to retrieve or playback a file from the peers 110 with a guaranteed level of service. More particularly, the user of the user platform 115 may initiate a request for playback or download of a file. The GQOS client 150 retrieve the metadata associated with the selected file and then start the requested function for the selected file from one of the reserved servers 105 that stores the requested file. The GQOS client 150 may also initiate a download of the requested file from the peers 110. The GQOS client 150 may use the retrieved metadata of the selected file to monitor the progress of the P2P download of the selected file as well as the progress of the transfer of the selected file from the reserved server 105. If the P2P download from the peers 110 is sufficient to support the requested playback or download, the GQOS client 150 may switch from the reserved server 105 to the P2P download by the peers 110.

While the transfer of the selected file is being sourced by the peers 110, The GQOS client 150 may also monitor the status of each of the subsequent segments of the selected file. If a subsequent segment has not or will not complete download by the time of download or playback by the peers 110, the GQOS client 150 may retrieve the subsequent segment from the reserved server 105. Accordingly, a user may obtain a guaranteed level of service from a P2P network without monopolizing the resources of a single server.

FIG. 2 illustrates an exemplary GQOS client 150 in accordance with another embodiment. It should be readily apparent to those of ordinary skill in the art that the GQOS client 150 depicted in FIG. 2 represents a generalized schematic illustration and that other components may be added or existing components may be removed or modified. Moreover, the GQOS client 150 may be implemented using software components, hardware components, or combinations thereof.

As shown in FIG. 2, the GQOS client 150 may comprise a control module 205 coupled to a memory 210 and an interface 215. The control module 205 may be configured to provide an execution platform for the functionality of the GQOS client 150 as described previously and in further detail below. The control module 205 may be implemented as an integrated circuit such as application specific integrated circuit, field programmable gate array or other similar programmable device, combination of circuits, microprocessor, or digital signal processor. Alternatively, the GQOS client 150 may be implemented as software program, application, subroutine, and/or function call. In yet other embodiments, the GQOS client 150 may be combination of hardware and software components as known to those skilled in the art.

The memory 210 may be configured to provide a storage function for the GQOS client 150. The memory 210 may be used, among others, as an area to store downloaded files or as temporary buffer for files being played in real time. The memory 210 may also store a software application that provides the functionality of the GQOS client 150. The memory 210 may be implemented using high speed memory such as dynamic random access memory or other similar technologies. In alternative embodiments, the memory 210 may be allocated in the main memory by the underlying operating system in response to the invocation of the GQOS client 150.

The interface 215 may be configured to provide a communication port for the control module 205 to interact with the operating system as well as the reserved servers 105 and peers 110. The interface 215 may be implemented as a standard interface such as peripheral control interface, SCSI, IEEE1394 in hardware embodiments or a software port in software embodiments.

Accordingly, the control module 205 may be configured to receive a request for playback or download of a selected file. The control module 205 retrieve the metadata associated the selected file through the interface 215 and then start the requested function for the selected file from one of the reserved servers 105 that stores the requested file. The control module 205 may also initiate a download of the requested file from the peers 110 to be stored in the memory 210. The control module 205 may use the retrieved metadata of the selected file to monitor the progress of the P2P download of the selected file from the peers 110 as well as the progress of the transfer of the selected file from the reserved server 105. If the P2P download from the peers 110 is sufficient to support the requested playback or download, the control module 205 may switch from the reserved server 105 to the P2P download by the peers 110.

While the transfer of the selected file is being sourced by the peers 110, the control module 205 may also monitor the status of each of the subsequent segments of the selected file. If a subsequent segment has not or will not complete download by the time of download or playback by the peers 110, the control module 205 may retrieve the subsequent segment from the reserved server 105. Accordingly, a user may obtain a guaranteed level of service from a P2P network without monopolizing the resources of a single server.

FIG. 3 illustrates an exemplary flow diagram 300 implemented by the control module 205 of the GQOS client 135 in accordance with yet another embodiment. It should be readily apparent to those of ordinary skill in the art that the flow diagram 300 depicted in FIG. 3 represents a generalized schematic illustration and that other steps may be added or existing steps may be removed or modified.

As shown in FIG. 3, in step 30S, the control module 205 of the GQOS client 150 may receive a request for playback and/or download of a selected file. The control module 205 may retrieve metadata associated with the selected file through interface 215 and store the metadata in the memory 210, in step 310. The metadata provides information such as the size of the file, location, number of segments, playback rates, etc.

In step 315, the control module 205 may be configured to initiate the requested action (playback or download) from the reserved server 105 that stores the selected file. The control module 205 may use the memory 210 as either a storage location for a file download or a buffer for a file playback.

Subsequently or substantially simultaneously, the control module 205 may also initiate a P2P download of the selected file from the peers 110, in step 320. The control module 205 may be configured to determine whether the next segment from the P2P download is ready based on the current position of the file from the reserved server 105, in step 325. If the next segment is ready for playback or download, the control module 205 may switch the playback or download to the P2P downloaded file, in step 330. Subsequently, the control module 205 may be configured to determine whether the last segment has been downloaded or played, in step 335. If the end of the file has not been reached, the control module 205 returns to the processing of step 325. Otherwise, the control module 205 terminates the file download or playback.

Returning to step 325, if the control module 205 determines that the next segment is not ready for the requested action, the control module 205 may retrieve the next segment from the reserved server 105, in step 345. Subsequently, the control module 205 proceeds to the processing of step 335.

FIG. 4 illustrates an exemplary block diagram of a computing platform 400 where an embodiment may be practiced. The functions of the operating system and GQOS client may be implemented in program code and executed by the computing platform 400. The operating system and delay process may be implemented in computer languages such as PASCAL, C, C++, JAVA, etc.

As shown in FIG. 4, the computer system 400 includes one or more processors, such as processor 402 that provide an execution platform for embodiments of the operating system and GQOS client. Commands and data from the processor 402 are communicated over a communication bus 404. The computer system 400 also includes a main memory 406, such as a Random Access Memory (RAM), where the operating system and GQOS client may be executed during runtime, and a secondary memory 408. The secondary memory 408 includes, for example, a hard disk drive 410 and/or a removable storage drive 412, representing a floppy diskette drive, a magnetic tape drive, a compact disk drive, etc., where a copy of a computer program embodiment for the operating system and GQOS client may be stored. The removable storage drive 412 reads from and/or writes to a removable storage unit 414 in a well-known manner. A user interfaces with the operating system and GQOS client with a keyboard 416, a mouse 418, and a display 420. A display adapter 422 interfaces with the communication bus 404 and the display 420. The display adapter also receives display data from the processor 402 and converts the display data into display commands for the display 420.

Certain embodiments may be performed as a computer program. The computer program may exist in a variety of forms both active and inactive. For example, the computer program can exist as software program(s) comprised of program instructions in source code, object code, executable code or other formats; firmware program(s); or hardware description language (HDL) files. Any of the above can be embodied on a computer readable medium, which include storage devices and signals, in compressed or uncompressed form. Exemplary computer readable storage devices include conventional computer system RAM (random access memory), ROM (read-only memory), EPROM (erasable, programmable ROM), EEPROM (electrically erasable, programmable ROM), and magnetic or optical disks or tapes. Exemplary computer readable signals, whether modulated using a carrier or not, are signals that a computer system hosting or running the present invention can be configured to access, including signals downloaded through the Internet or other networks. Concrete examples of the foregoing include distribution of executable software program(s) of the computer program on a CD-ROM or via Internet download. In a sense, the Internet itself, as an abstract entity, is a computer readable medium. The same is true of computer networks in general.

While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments without departing from the true spirit and scope. The terms and descriptions used herein are set forth by way of illustration only and are not meant as limitations. In particular, although the method has been described by examples, the steps of the method may be performed in a different order than illustrated or simultaneously. Those skilled in the art will recognize that these and other variations are possible within the spirit and scope as defined in the following claims and their equivalents. 

1. A method for playing a file, the method comprising: initiating a playback for a selected file on a reserved server, wherein the selected file is also distributed in segments across a peer-to-peer network; initiating a retrieval of the selected file from the peer-to-peer network; ordering the retrieved segments of the selected file for playback and switching playback of the selected file from the peer-to-peer network in response to retrieved segments ready for playback.
 2. The method of claim 1, further comprising: maintaining an index structure for monitoring the playback of the selected file.
 3. The method of claim 1, further comprising: determining whether a subsequent segment of the selected file is ready for playback; and retrieving the subsequent segment from the reserved server in response to determining the subsequent segment of the selected file is not ready for playback.
 4. The method of claim 3, further comprising: determining whether the next subsequent segment of the selected file is ready for playback from the peer-to-peer network; and switching the playback of the selected file to the next subsequent segment of the selected file.
 5. The method of claim 1, wherein the peer-to-peer network is one of an unstructured peer-to-peer network and a structured peer-to-peer network.
 6. The method of claim 1, wherein the peer-to-peer network is one of Bit Torrent, Napster, Gnutella, and KaZaA.
 7. The method of claim 1, wherein the peer-to-peer network is one of Chord, Pastry, Tapestry, Content Addressable Network, and Tulip.
 8. An apparatus comprising means to implement the method of claim
 1. 9. A computer-readable medium comprising computer-executable instructions for performing the method of claim
 1. 10. An apparatus for delivering a file, the apparatus comprising: a control module configured to interface with a reserved server and a peer-to-peer network, wherein the control module is configured to receive a request for a file, initiate a playback of the file on a reserved server; initiate a retrieval of the file from the peer-to-peer network, wherein the file is stored in segments in the peer-to-peer network; ordering the retrieved segments of the file for playback; and switch playback of the file from the peer-to-peer network in response to retrieved segments ready for playback.
 11. The apparatus of claim 10, wherein the control module is further configured to maintain an index structure for monitoring the playback of the selected file.
 12. The apparatus of claim 10, wherein the control module is further configured to determine whether a subsequent segment of the selected file is ready for playback and retrieve the subsequent segment from the reserved server in response to determining the subsequent segment of the selected file is not ready for playback.
 13. The apparatus of claim 12, wherein the control module is further configured to determine whether the next subsequent segment of the selected file is ready for playback from the peer-to-peer network and switch the playback of the selected file to the next subsequent segment of the selected file.
 14. The apparatus of claim 10, wherein the peer-to-peer network is one of an unstructured peer-to-peer network and a structured peer-to-peer network.
 15. The apparatus of claim 10, wherein the peer-to-peer network is one of Bit Torrent, Napster, Gnutella, and KaZaA.
 16. The apparatus of claim 10, wherein the peer-to-peer network is one of Chord, Pastry, Tapestry, Content Addressable Network, and Tulip.
 17. A system for delivering a file, the system comprising: a reserved server configured to store a plurality of files; a peer-to-peer network configured to store the plurality of files, wherein each file is distributed through the peer-to-peer network as segments; and a quality of service client configured to initiate a playback for a user-selected file on the reserved server; initiate a retrieval of the selected file from the peer-to-peer network in response to the initiation of the playback; order the retrieved segments of the selected file for playback; and switch playback of the selected file from the peer-to-peer network in response to retrieved segments ready for playback.
 18. The system of claim 17, wherein the quality of service client is further configured to maintain an index structure for monitoring the playback of the selected file.
 19. The system of claim 17, wherein the quality of service client is further configured to determine whether a subsequent segment of the selected file is ready for playback and retrieve the subsequent segment from the reserved server in response to determining the subsequent segment of the selected file is not ready for playback.
 20. The system of claim 19, wherein the quality of service client is further configured to determine whether the next subsequent segment of the selected file is ready for playback from the peer-to-peer network and switching the playback of the selected file to the next subsequent segment of the selected file.
 21. The system of claim 17, wherein the peer-to-peer network is one of an unstructured peer-to-peer network and a structured peer-to-peer network.
 22. The system of claim 17, wherein the file is a music file.
 23. The system of claim 17, wherein the file is a video file.
 24. A method for playing a file, the method comprising: initiating a retrieval of the selected file from the peer-to-peer network, wherein the selected file is also distributed in segments on a reserved server; ordering the retrieved segments of the selected file for playback and switching playback of the selected file from the peer-to-peer network to the reserved server in response to retrieved segments ready for playback and when at least one of the segments is not available from the peer-to-peer network.
 25. A method for playing a file, wherein segments of the file are distributed in a peer-to-peer network and a reserved server, the method comprising: requesting segments of the file from both the peer-to-peer network and the reserved server; scheduling retrieval of segments of the selected file from the peer-to-peer network and the reserved server based on responses from the peer-to-peer network and the reserved server; and switching playback of segments of the selected file based on the retrieval of the segments from the peer-to-peer network and the reserved server. 